In `@web/components/ui/PasswordStrength.tsx`:
- Around line 13-57: The password strength meter in PasswordStrength.tsx uses a
length criterion of 8 (criteria.length: password.length >= 8) which conflicts
with the form validation that allows 6-char passwords; update the length
threshold in the useMemo block (the criteria object used to compute
score/label/metCriteria and returned as score/label) to match the form
validation (change criteria.length to password.length >= 6) or, if you prefer
raising validation, update the form minimum to 8—ensure the change is applied
where criteria is defined in the useMemo and that the normalized score/label
logic (s and l) remains consistent with the new threshold.
- Line 74: The container div in PasswordStrength (the element rendered in
web/components/ui/PasswordStrength.tsx with aria-label="Password strength
indicator") uses aria-label without an explicit role, so add role="region" to
that div to ensure the aria-label is recognized by assistive tech; update the
JSX for the div that currently has className="w-full flex flex-col gap-2 mt-2"
and aria-label to include role="region" so the label becomes effective.
- Around line 121-124: Replace the visually hidden <div role="status"> live
region in the PasswordStrength component with a semantic <output> element:
locate the block that renders the sr-only live region and change it to use
<output> (keep className="sr-only" and aria-live="polite" but remove
role="status"), preserving the text content "Password strength: {label}." and
the conditional hint based on score so screen readers still receive the same
message.

In `@mobile/components/ui/hapticUtils.js`:
- Around line 13-49: There are many near-identical haptic wrapper files causing
import sprawl; create a single barrel export file (e.g., index.js) that
re-exports all the haptic wrappers so screens can import from the barrel instead
of individual files. Locate the wrapper creator withHapticFeedback in
hapticUtils and the one-line wrapper modules (e.g., HapticButton, HapticCard,
HapticFAB, etc.), then add an index that imports each wrapper by name and
re-exports them (export { default as HapticButton } from './HapticButton';
etc.), update import sites to use the barrel, and ensure the exported names
match the components’ display names or default exports so existing references
continue to work.
- Around line 19-29: The handlePress callback calls Haptics.impactAsync without
handling its Promise; update the useCallback for handlePress to await
Haptics.impactAsync inside a try/catch (or append .catch()) so rejections are
swallowed and won't cause unhandled promise crashes, keeping the originalHandler
invocation intact; reference the handlePress function and Haptics.impactAsync
and ensure the change preserves the existing behavior (trigger haptics when
appropriate and then call originalHandler(...args)).

In `@web/components/ui/PasswordStrength.tsx`:
- Line 74: In the PasswordStrength component replace the generic div that uses
role="region" with a semantic <section> element (keep the same className and
aria-label), i.e. change the element around the password strength UI in
PasswordStrength.tsx so it becomes a section with aria-label="Password strength
indicator" and remove the explicit role attribute; this keeps behavior and
styling intact while using the semantic element instead of div+role.
- Around line 25-48: In PasswordStrength.tsx the reachable-score bug comes from
always incrementing s for criteria.length so any >=6-char password becomes at
least score 2; remove the automatic length bonus (delete or disable the "if
(criteria.length) s++" increment) so length only gates scoring and only
complexity increments s (via complexity >=2 / >=4 checks), leaving s=1 =>
"Weak", s=2 => "Fair", s=3 => "Good", s>=4 => "Strong" (refer to variables s, l,
criteria.length and the complexity calculation).